home *** CD-ROM | disk | FTP | other *** search
- Path: news.iadfw.net!usenet
- From: Mark Nelson <markn@airmail.net>
- Newsgroups: comp.lang.c++
- Subject: Re: [Q]Serial Communications under OWL 2.0
- Date: Fri, 23 Feb 1996 09:17:41 -0600
- Organization: customer of Internet America
- Message-ID: <312DDA95.2013@airmail.net>
- References: <4gdagj$2ml@antares.en.com>
- NNTP-Posting-Host: dal21-09.ppp.iadfw.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0GoldB1 (Win95; I)
-
- _______ wrote:
- >
- > I have a serial communications library which I developed using interrupts. The
- > library works fine under DOS. The code will compile and run, but generates an
- > exception when the Serial port is initialized.
- >
- > Does anyone know of a compiler option or other setting that I am missing?
- >
- > Thanks for any help.
- >
- > Eric Conko
-
- Judging from your subject line, it looks as though you are saying this
- problem occurs when you try to use the library under Windows. If this is
- the case, you need to use the Windows Comm API. There are something like
- nine different functions to work with serial ports under Windows. Writing
- directly to UART and installing interrupt handlers isn't really an option
- at the application program level.
-
- My book "Serial Communications: A C++ Developer's Guide" has a C++
- class that lets you access the com ports using exactly the same function
- calls under MS-DOS and Windows. (You can get more info on the book
- on my Web Page.) But you don't really need my book to just read and
- write. Use your online help to look up OpenComm(), and follow the links
- from there.
-
- Mark Nelson
- http://web2.airmail.net/markn - RS-232 articles online + book info
-